Vodacom Financial Services: Payment Solutions - Merchant Payment Page Integration
Payment Broker

Contents / Tables / Figures / Related Documentation
Version 1.4.1

1. Contents

Table 1. Contents
#		Chapter
1.		Introduction
2.		Configuration Information
	2.1.	- Minimum API Developer Requirements
	2.2.	- Payment Gateway: Operational and Maintenance Hours
	2.3.	- Security
	2.3.1.	- Transport Layer Security and Firewall Requirements
	2.3.2.	- Payload Encryption
	2.3.3	- Control Key
	2.4.	- Parameterised Data
	2.5.	- Role-players in the system
	2.5.1.	Payment Broker
	2.5.2.	- Payment Gateway
	2.5.3.	- Customer
	2.5.4.	Merchant
3.		- Payment Types Accepted
4.		- Implementation
	4.1.	- Payment Broker
	4.1.1.	- Payment Broker API Documentation
	4.1.2.	- Payment Broker Services
	4.1.3.	- VFS Payment Broker End-Points
	4.2.	- Payment Broker Process Flow
	4.3.	- Connect Create API
	4.3.1.	- Authorisation Object
	4.3.2.	- Form Object
	4.3.3.	- Product Object
	4.3.4.	- Webhooks Object
	4.3.5.	- Expiry Object
	4.3.6.	- ConnectCreate RESPONSE Object
	4.4.	- ConnectDelete API
	4.5.	- ConnectVerify API
	4.6.	- WebHooks
	4.6.1.	- Webhook Object
	4.6.2.	- Create Webhook Template
	4.6.3	- ConnectDelete Template
	4.6.4.	- ConnectVerify Template

Table 2. Tables
#	Tables
2.1	Table 4: Firewall Request for Asynchronous Callbacks
2.2	Table 5: Payment Gateway White-List Requirements
2.3	Table 6: Merchant Prerequisites
2.4	Table 7: Connect.Create Object Fields
2.5	Table 8: Connect.Create.Authorisation Object Fields
2.6	Table 9: Connect.Create.Form Object Fields
2.7	Table 10: Connect.Create.Form.Products Object Fields
2.8	Table 11: Connect.Create.Form.WebHooks Object Fields
2.9	Table 12: Connect.Create.Expiry Object Fields
2.10	Table 13: Connect/Create RESPONSE Object
2.11	Table 14: Connect.Delete Object Fields
2.12	Table 15: Connect.Verify Object Fields
2.13	Table 16: Connect.Create Webhooks Template JSON Fields
2.14	Table 17: Connect.Delete Webhooks Template JSON Fields
2.15	Table 18: Connect.Verify Webhooks Template JSON Fields

Table 3. Figures
#	Figures
3.1	Figure 1: PayBroker Process Flow
3.2	Figure 2: Connect.Create JSON Template
3.3	Figure 3: Connect.Create JSON Sample Request
3.4	Figure 4: Connect.Create Response JSON Sample
3.5	Figure 5: Connect.Delete JSON Template
3.6	Figure 6: Connect.Verify JSON Template
3.7	Figure 7: Connect.Create Webhooks Template
3.8	Figure 8: Connect.Create Webhooks Template - Base64 Encoded
3.9	Figure 9: Connect.Delete Webhooks Template
3.10	Figure 10: Connect.Delete Base64 Encoded Template
3.11	Figure 11: Connect.Verify Webhooks Template
3.12	Figure 12: Connect.Verify Webhooks Base64 Encoded Template

Table 4. Referenced Documentation
Revision	Document	Description
2.51	Recurring Payments Confluence / Web	A service to ecommerce merchants for performing Scheduled Transaction Payments on the payment gateway at a recurring interval determined by the merchant.
3.3.91	Payments Page Confluence / Web	This document presents a guide for merchants wishing to make use of the Vodacom Financial Services Payment Gateway recurring transaction processing service for eCommerce transactions via credit card.
1.21	Payment Broker Confluence / Web	The Payments Broker will facilitate the creation of an encoded URL that will act as an intermediary between the customer and the Payment Gateway payment page. The merchant then makes this URL available to their customer.
1.1	Save Card Confluence	Save card details allows merchants to pass their unique merchant Id and customer Id and have their customers previously saved card automatically display as a payment option on the payment page.
1.2	Payment Response Re-Retry Confluence	The queuing mechanism implemented on the Payment Gateway to retry responses to merchants on the outcome of a payment request, in order to guarantee the delivery of that response.